Hi,
I want to be able to check what has changed between two baselines of a module. These might be non-consecutive (e.g. v1.0 to v3.0) hence change bars won't suffice (they're only what's change since last baseline) and I need other tools.
Doors provides two options, but these have shortcomings:
1. "Baseline>Compare". This checks object text only as far as I can see. Also, the report is very simple and can't be printed
2. "Tools>Compare Modules". This creates new links within the doc to the older baseline - these are unhelpful links to have in place. Worse, if there are already such links, it seems to delete and replace them which is not viable for us. And while other attributes can be checked, I find the report format (in separate col) quite confusing.
Hence I don't find either of these a viable solution to a fairly basic need.
Have I missed something? Are there other approaches out there?
To IBM respondents, are there existing enhancement requests in this area that are pending/planned?
Thanks,
Kieran
kierant - Wed Apr 01 10:00:46 EDT 2009 |
|
Re: Drawbacks with module comparison utilities Peter_Albert - Wed Apr 01 10:48:30 EDT 2009
Hi Kieran,
attached is an include file for displaying differences between two selectable baselines in a layout DXL column. See routine header for information on how the routine is called.
Per default it shows the difference w.r.t to all attributes visible in the current view, but you can force the attributes to be compared by specifiying e.g.
#include <../layout/include/versionCompare.inc> versionCompare__use_view =
false versionCompare__attribute_list = create() put(versionCompare__attribute_list, 0,
'Object Text') put(versionCompare__attribute_list, 0,
'Comments') modifications()
As it is layout DXL, the performance is relatively slow, but it is straightforward to make it an attribute DXL if required.
Regards,
Peter
Attachments
attachment_14236228_versionCompare.inc
|
|
Re: Drawbacks with module comparison utilities kierant - Wed Apr 01 11:58:15 EDT 2009 Peter_Albert - Wed Apr 01 10:48:30 EDT 2009
Hi Kieran,
attached is an include file for displaying differences between two selectable baselines in a layout DXL column. See routine header for information on how the routine is called.
Per default it shows the difference w.r.t to all attributes visible in the current view, but you can force the attributes to be compared by specifiying e.g.
#include <../layout/include/versionCompare.inc> versionCompare__use_view =
false versionCompare__attribute_list = create() put(versionCompare__attribute_list, 0,
'Object Text') put(versionCompare__attribute_list, 0,
'Comments') modifications()
As it is layout DXL, the performance is relatively slow, but it is straightforward to make it an attribute DXL if required.
Regards,
Peter
Thanks alot Peter for speedy reply - this utility looks great.
To IBM - I think this or equivalents need to be product-ised - it shouldn't be up to teams to create scripts in reponse to what is a general/fundamental need. I will log an enhancement request.
|
|
Re: Drawbacks with module comparison utilities adevicq - Mon Jun 15 09:58:11 EDT 2009
Hi,
I also have this attached script. I don't remember who is the author, but it is pretty simple to use and it displays changes on selected attributes in colour.
To use it, create a Layout DXL column and insert the following code:
string attributeToGetHistoryFrom[] = { "Object Heading",
"Object Text" }
// just add any new Attributes you want history displayed on into this array
#include "<your include path>/displayAttributesChanges.dxl"
Alain
|
|
Re: Drawbacks with module comparison utilities ChrisAnnal - Mon Mar 28 10:33:02 EDT 2011 adevicq - Mon Jun 15 09:58:11 EDT 2009
Hi,
I also have this attached script. I don't remember who is the author, but it is pretty simple to use and it displays changes on selected attributes in colour.
To use it, create a Layout DXL column and insert the following code:
string attributeToGetHistoryFrom[] = { "Object Heading",
"Object Text" }
// just add any new Attributes you want history displayed on into this array
#include "<your include path>/displayAttributesChanges.dxl"
Alain
Hi Alain,
I saw your response to this thread mentions to "see attached script" (displayAttributesChanges.dxl) but that script wasn't attached. Do you still have this script?
Thanks a lot!
-Chris
Chris Annal
SW Test Engineer / DOORS Database Administrator
Sensis Corporation, East Syracuse, New York
chrisa@sensis.com
|
|
Re: Drawbacks with module comparison utilities adevicq - Tue Mar 29 03:42:07 EDT 2011 ChrisAnnal - Mon Mar 28 10:33:02 EDT 2011
Hi Alain,
I saw your response to this thread mentions to "see attached script" (displayAttributesChanges.dxl) but that script wasn't attached. Do you still have this script?
Thanks a lot!
-Chris
Chris Annal
SW Test Engineer / DOORS Database Administrator
Sensis Corporation, East Syracuse, New York
chrisa@sensis.com
Oops!
Here it is...
Attachments
attachment_14599783_DisplayAttributesChanges.dxl
|
|